Validate test binaries upon code changes#780
Conversation
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
Removed signal alarm handling in exception block.
Updated the script to log output and check for errors.
for more information, see https://pre-commit.ci
Updated script to accept branch and suffix as arguments, streamlined output file naming.
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
Updated script usage instructions to include PATH_TO_POSYODN_DATA.
…s, generate baseline, add more specificity to compare_runs
… into et-validation
for more information, see https://pre-commit.ci
c9b265c to
d95c17a
Compare
for more information, see https://pre-commit.ci
… into et-validation
for more information, see https://pre-commit.ci
|
@elizabethteng , during a dev meeting we saw that there were some differences between values when comparing two branches according to these tests. I'm planning to help by looking into the source of those differences. Can you please post here which two branches produced those differences if you have them on hand? |
|
At least in my testing, I noticed differences between branches that would occur only for This difference indeed seems to be caused by the randomization used in |
Uh oh!
There was an error while loading. Please reload this page.